When will `git pull --rebase` get me in to trouble?

Posted by Gabe Hollombe on Stack Overflow See other posts from Stack Overflow or by Gabe Hollombe
Published on 2010-04-07T05:46:24Z Indexed on 2010/04/07 5:53 UTC
Read the original article Hit count: 300

Filed under:
|
|

I understand that when I use git pull --rebase, git will re-write history and move my local commits to occur after all of the commits in the branch I just pulled from.

What I don't understand is how this would ever be a bad thing. People talk about getting in to trouble with git pull --rebase where you can end up with a branch that other people can't pull from. But I don't get how that's possible since all you're doing is replaying your local, not-yet-public, commits on top of the branch you pulled from. So, what's the problem there?

© Stack Overflow or respective owner

Related posts about git

Related posts about pull